I've found that Jeff and Russ above are generally correct; there is no simple way to actually do it, but you can simplify your process somewhat. In my case, I had to find a way to wrestle 3500 pages of data spread across 49 Word files. These files had been updated and maintained haphazardly for several years and were as a result were unstable and prone to crash. There was no way I was going to continue to use Word to fix that, not if I wanted to retain what was left of my sanity. This situation is precisely what FM is good for. It took the better part of a year, but I got it under control...for a given value of "control". As a result, my workflow looks a lot like CarolineTa's above. Depending on the data changes, your process may be simple or complex. I would never ask the engineers to learn FM; they don't need it and it would just lead to dogs and cats living together--mass hysteria! (Bill Murray, Ghostbusters) For simplicity's sake, I generally work as follows: 1. I ask the engineers to submit their changes in Word with change tracking turned on and a comment noting what changes have been made. (This also helps with QA review in the document release process.) 2. I copy and past the changes into the FM document. (I can usually get away with pasting as plain text. Your mileage may vary, of course.) If the changes are large enough, I import the Word file into FM and reformat as necessary. 3. Instead of embedding image files, I link to them; then I can simply replace the file in an online repository and update FM later. 4. Once the changes are added and formatted, I create a PDF of the FM file and submit for review. The engineers and QA are happy with this arrangement as it captures all changes; I'm happy because I don't have to stay until two o' clock in the morning trying to get Word to print without losing my mind. Hope this helps! -terry-
... View more